Skip to content

fix(paths): fix the determination of execution path #310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 18, 2016

Conversation

Brocco
Copy link
Contributor

@Brocco Brocco commented Mar 18, 2016

Windows does not populate this fix allows for determination
of the directory from which an ng command was executed
Fixes #297

Windows does not populate  this fix allows for determination
of the directory from which an ng command was executed
Fixes angular#297
@filipesilva filipesilva merged commit f2f5ff9 into angular:master Mar 18, 2016
@Brocco Brocco deleted the windows-generate-bug branch March 20, 2016 03:46
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ng generate component fails
2 participants